Systems and methods for dynamic mobile printing based on scheduled events

ABSTRACT

Systems and methods are disclosed method for dynamic mobile printing based on scheduled events. One method includes receiving, from a device associated with a user, an identifier associated with the user and a print request, the print request including one or more print items to be printed; accessing, by a server, a calendar of the user based on the received identifier associated with the user; determining, by the server, whether an event of the calendar is scheduled for a time of interest; locating, by the server, a printer near a location of the event when the event is scheduled for the time of interest; and transmitting, by the server, the one or more print items to the printer near the location of the event.

TECHNICAL FIELD

Various embodiments of the present disclosure relate generally toincreasing productivity and accessibility of resources in a physicalfacility. More specifically, exemplary embodiments of the presentdisclosure relate to systems and methods for reducing an individual'stime spent on accessing information or making a request relating to afacility, and improving the accuracy and efficiency in fulfilling arequest via mobile communication.

BACKGROUND

In any facility, such as an office building, apartment building,commercial building (e.g., mall), sporting/music venue, or the like,people often find themselves desiring information about the facilityand/or desiring to submit a request relating to their interaction withthe facility. For example, people may desire information about wherevarious rooms, stores, or amenities are located. In addition, oralternatively, people might desire to submit various requests, such asrequests to have certain facilities repaired, or to reserve portions ofa facility for private use. As a result, building managers traditionallyerected physical directories, or distributed paper directories thatindividuals could consult to explore the facility. Also, managementwould traditionally implement procedures for making requests, such as byfilling out a request form with a facilities department, or submitting aconference room request form, etc.

In the context of commercial buildings, in particular, many employersimplement programs to train employees on how to submit request forms toaddress various issues. In addition to the time and expense spent onthese training programs, the actual request may take time beingsubmitted to the appropriate department and may lack sufficientspecificity for the request to be implemented. In the meantime, orinstead of sending the request, the employee may spend time attemptingto resolve the request on his or her own. This may result is a loss ofemployee productivity and/or an inaccurate or incomplete resolution tothe initial request. For example, an employee may wish to report aproblem with his or her printer to the information technology (IT)department of his or her employer. In order to do this, the employee mayhave to make a call, compose an email, and/or fill out a form making arequest; wait to communicate with an IT officer; and check back with theIT officer to obtain the status of the request. These steps may take asignificant amount of time, reducing employees' happiness andproductivity, and may result in the request not being timely completed.

Accordingly, a need exists for systems and methods for facilitatingaccurate, efficient and rapid processing of facilities requests. Thepresent disclosure is directed to, among other things, improving anexperience and reducing an amount of time spent on making a facilitiesrequest, and to improving the accuracy of fulfilling a request viamobile communication.

SUMMARY OF THE DISCLOSURE

According to certain embodiments, a computer-implemented method isdisclosed for dynamic mobile printing based on scheduled events, themethod comprising: receiving, from a device associated with a user, anidentifier associated with the user and a print request, the printrequest including one or more print items to be printed; accessing, by aserver, a calendar of the user based on the received identifierassociated with the user; determining, by the server, whether an eventof the calendar is scheduled for a time of interest; locating, by theserver, a printer near a location of the event when the event isscheduled for the time of interest; and transmitting, by the server, theone or more print items to the printer near the location of the event.

According to certain embodiments, a system is disclosed for dynamicmobile printing based on scheduled events, the system comprising: amemory storage device storing instructions for dynamic mobile printingbased on scheduled events; and one or more processors configured toexecute the instructions to perform a method including: receiving, froma device associated with a user, an identifier associated with the userand a print request, the print request including one or more print itemsto be printed; accessing, by a server, a calendar of the user based onthe received identifier associated with the user; determining, by theserver, whether an event of the calendar is scheduled for a time ofinterest; locating, by the server, a printer near a location of theevent when the event is scheduled for the time of interest; andtransmitting, by the server, the one or more print items to the printernear the location of the event.

According to one embodiment, a computer-readable medium is disclosedthat stores instructions that, when executed by a processor, cause theprocessor to execute a method dynamic mobile printing based on scheduledevents, the method comprising: receiving, from a device associated witha user, an identifier associated with the user and a print request, theprint request including one or more print items to be printed;accessing, by a server, a calendar of the user based on the receivedidentifier associated with the user; determining, by the server, whetheran event of the calendar is scheduled for a time of interest; locating,by the server, a printer near a location of the event when the event isscheduled for the time of interest; and transmitting, by the server, theone or more print items to the printer near the location of the event.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments. The objects and advantages of the disclosedembodiments will be realized and attained by means of the elements andcombinations particularly pointed out in the appended claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 is a schematic diagram of an environment in which a user mayidentify and submit information related to a request for information orservices relating to a facility, according to an exemplary embodiment ofthe present disclosure.

FIG. 2 is a diagram of a system configured to enable users to identifyand submit information related to a request for information or servicesrelating to a facility, according to an exemplary embodiment of thepresent disclosure.

FIG. 3 is a schematic diagram of devices and indicia configured toenable users to identify and submit information related to a request forinformation or services relating to a facility, according to anexemplary embodiment of the present disclosure.

FIG. 4 is a flow diagram of an exemplary method for enabling users toidentify and submit information related to a request for information orservices relating to a facility, according to an exemplary embodiment ofthe present disclosure.

FIG. 5 is a screenshot of an exemplary mobile application for enablingusers to identify and submit information related to a request forinformation or services relating to a facility, according to anexemplary embodiment of the present disclosure.

FIG. 6 is a schematic diagram of a device and indicia for enabling usersto log-in to a mobile application for identifying and submittinginformation related to a request for information or services relating toa facility, according to an exemplary embodiment of the presentdisclosure.

FIGS. 7A-7D are screenshots of an exemplary mobile application forenabling users to identify and submit information related to a requestfor services relating to a facility, according to an exemplaryembodiment of the present disclosure.

FIGS. 8A-8E are screenshots of an exemplary mobile application forenabling users to identify and submit information related to a requestfor information relating to a facility, according to an exemplaryembodiment of the present disclosure.

FIGS. 9A-9B are screenshots of an exemplary mobile application fordynamic mobile printing based on scheduled events, according to anexemplary embodiment of the present disclosure.

FIG. 10 is a flow diagram of an exemplary method for dynamic mobileprinting based on scheduled events according to an exemplary embodimentof the present disclosure.

FIG. 11 is a simplified functional block diagram of a computer that maybe configured as a device or server for executing the methods of FIGS. 4and 10, according to exemplary embodiments of the present disclosure.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the exemplary embodiments of thedisclosure, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

The present disclosure describes systems and methods for improving anindividual's or user's interaction with a facility and/or the people andservices associated with the facility; to reducing an amount of timespent on making a request; and to improving the accuracy of fulfilling afacilities-related request via mobile communication.

According to embodiments of the present disclosure, a user may use amobile device in communication with a wireless (“Wi-Fi”) router or awireless network that is in communication with the Internet to submit arequest for information or services. Although described herein as oftenpertaining to mobile devices and applications, it should be appreciatedthat the user may be operating any type of electronic device, whethermobile or not. In one embodiment, the user may submit the request to aserver by submitting an image of the user's identifier (e.g., ID,workplace badge, or building badge), and/or an asset's, component's, orentity's identifier to a server via the Internet or other network. Basedon the submitted identifier(s), the server may access a database toretrieve information regarding the user or entity associated with theidentifier, and identify the user's location based on the leveragedWi-Fi router or any other location-specific indicators. Alternatively,the location of the user may be identified using global positioning(“GPS”) coordinates of the user. The server may then prompt the user tosubmit a specific request based on the identified asset, component, orentity and/or location of the user. Once received, the server mayprocess the request and provide the user with information regarding thestatus of the request and may also update any databases and/or provideother users information regarding the request.

According to another embodiment of the present disclosure, a user mayuse a mobile device in communication with the Wi-Fi router or thewireless network that is in communication with the Internet to scheduleprinting and/or to print based on the schedule of the user and/or alocation of the user. In an embodiment, the user may create, access,update, and/or store events on his or her calendar that is stored on acalendar server system. When creating an event, the user may provide thetime and date of the event and may provide a location of the event. Theuser may enter the location of the event and/or have a server identifythe user's location for the location of the event. The user may alsoprovide one or more documents to be printed for the event. If the userprovides documents for the event, a server may store the documents, andprint the documents to a printer near the event's location at or nearthe time of the event. Alternatively, or additionally, the user mayrequest that the server print the documents at a user-provided locationand a user-provided time.

Referring now to the figures, FIG. 1 is a schematic diagram of anenvironment in which a user may identify and submit information relatedto a request for information, printing, or services relating to afacility, according to exemplary embodiments of the present disclosure.Specifically, FIG. 1 depicts and environment or facility 100, which maybe an office building, apartment building, commercial building (e.g.,mall), sporting/music venue, or the like. In one embodiment, environmentor facility 100 may be a workplace for a plurality of individuals orusers 112 (“people,” “individuals,” and “users” are used interchangeablyherein). In one embodiment, facility 100 may include one or morephysical spaces or rooms 110. Of course, it should be appreciated thatfacility 100 may span any number of campuses, buildings, or cities.Facility 100 may be a complex network of buildings for a multi-nationalcorporation spread around the globe. Alternatively, facility 100 may beas small as a single office.

As described above, facility 100 may be configured to enable users toidentify and submit information related to a request for information,printing, or services relating to the facility. Accordingly, facility100 may be provided with one or more systems, devices, and indicia withwhich users may interact to submit requests for information or servicesfrom those systems and devices. For example, facility 100 may beprovided with a server system 132 provided in communication with one ormore wireless access points (“WAPs”) 134. Server systems 132 may includedatabases and processors configured to execute methods of enabling usersto request information or services relating to the facility. Inaddition, server systems 132 may include any number of servers relatingto the facility and/or a business occupying the facility, such as e-mailservers, printing servers, calendar servers, helpdesk servers,information technology and/or Internet technology (collectively, “IT”)servers, human resources (“HR”) servers, employee servers, documentmanagement servers, etc., as will be described in more detail below.

In addition, one or more of users 112 (which may be owners and/oremployees of the business(es) occupying the facility 100) may eachpossess one or more electronic devices 114, for interacting with thefacility 100, and more specifically, for interacting with the serversystems 132 and/or WAPs 134. In one embodiment, the users' electronicdevices 114 may be any type of mobile phone, personal data assistant(“PDA”), tablet, personal computer (“PC”), an electronic kiosk, or anyother electronic device that may send and receive information via awireless network, such as over the Internet or a local- or wide-areanetwork (“LAN” or “WAN”). One or more of the electronic devices 114 mayinclude an optical component configured to capture and/or recognize animage, and save and/or transmit the image via the Internet or a wirelessnetwork. For example, the optical component may be a camera, scanner, orany other suitable optical component. The electronic devices 114 mayalso be provided with a Bluetooth or other radio frequency communicationprotocol, and/or a near field communication (“NFC”) device, forcommunicating with other suitably-provisioned devices. Alternatively, orin addition to an optical component, the electronic devices 114 mayinclude one or more audio and/or video components configured to captureand/or recognize a sound, series of sounds, and/or frame(s), and saveand/or transmit the sound(s) and/or frame(s) via the wireless network.For example, an audio component may include a microphone, or any othersuitable audio component, and a video component may include any type ofcamera.

In one embodiment, an optical component of each of electronic devices114 may be used to capture and/or recognize an identifier or indicia 116associated with any entity or asset of the facility 100, such as a user,a piece of equipment (e.g. printer 122, laptop 118, 124, tablet,television, desk, chair, etc.), a physical location (e.g. officebuilding, conference room 120, office 130, etc.), or any other entity.The indicia 116 may be any machine-readable visual representationcapable of being captured and/or scanned by an optical component of anelectronic device 114. For example, the indicia 116 may be a one, two,or three dimensional barcode, or any other visual identifier.Alternatively, the indicia 116 may include alphanumeric indicia, such asa name, room number, serial number, etc., which the electronic device114 or related device or module may decode or otherwise recognize asindicative of the entity or asset of the facility 100. In oneembodiment, the indicia 116 may be associated with an entity or asset,and the association may be saved in retrievable memory, such as on acomputer readable medium associated with server systems 132.

FIG. 2 is a diagram of a system 200 configured to enable users toidentify and submit information related to a request for information,printing, or services relating to a facility, according to an exemplaryembodiment of the present disclosure. In one embodiment, system 200 mayinclude one or more of HR server systems 202, IT server systems 204,asset management server systems 206, facilities server systems 208,calendar server systems 222, and finance server system 224. System 200may further include mobile facilities request server systems 205(hereafter, “request server 205”), which may include one or moredatabases 210, one or more processors 212, and/or one or more userinterface (“UI”) modules 214. System 200 may further include or beprovided in communication with a plurality of mobile devices 216. Asdescribed above, mobile devices 216 may correspond to one or more ofelectronic devices 114, which may be any type of mobile phone, PDA,tablet, PC, an electronic kiosk, or any other electronic device that maysend and receive information via a wireless network 218, such as overthe Internet or LAN or WAN. In addition, request server 205 maycorrespond to server systems 132 provided in communication with one ormore WAPs 134 within a facility 100, and users may interact with requestserver 205 via any electronic devices 114 and/or mobile devices 216.

In one embodiment, a record of an association of an identifier of anasset or entity saved in memory may be located in one or more locationsbased on one or more characteristics of the entity. These locations maybe servers or other suitable devices configured to house and accesscomputer readable memory. For example, in an organization, such as alarge corporation, educational organization, government agency, etc., aseparate server may store information for a particular department. Inthe exemplary example shown in FIG. 2, an organization may have anetwork 220 with separate servers, such as the HR server systems 202,configured to store, share, and update, information regarding employees;the IT server systems 204, configured to store, share, and updateinformation regarding electronic equipment and requests to repairelectronic equipment; the asset management server systems 206,configured to store, share, and update information regarding physicalproperty; the facilities server systems 208, configured to store, share,and update information regarding various buildings and offices that arepart of the organization, the calendar server systems 222, configured tostore, share, and update information regarding employees' calendars,and/or finance server systems 224, configured to store, share, andupdate information regarding costs and charges.

The servers may communicate with one or more servers, such as requestserver 205, having database(s) 210, processor(s) 212, and UI module(s)214, via any LAN and/or WAN. The communication may be through wires orwirelessly via the Internet or LAN or WAN, or any other suitable means.The servers, such as request server 205, may receive and transmitinformation from devices, such as mobile devices 216 and other devicesthat may connect to request server 205. Each server systems, such as HRserver systems 202, IT server systems 204, asset management serversystems 206, facilities server systems 208, calendar server systems 222,and/or finance server systems 224, may communicate directly with eachother via the network 220 or through a server or servers, such asrequest server 205, or any other server and/or server system.

In one embodiment, database(s) 210 may include any type of RAM or ROMembodied in a physical storage medium, such as magnetic storageincluding floppy disk, hard disk, or magnetic tape; semiconductorstorage such as solid state disk (“SSD”) or flash memory; optical discstorage; or magneto-optical disc storage. In addition, processor(s) 212may include one or more processors for processing data according toinstructions stored in the memory. The functions of the processor may beprovided by a single dedicated processor or by a plurality ofprocessors. Moreover, the processor may include, without limitation,digital signal processor (“DSP”) hardware, or any other hardware capableof executing software. The UI module(s) 214 may include any type orcombination of programs for generating UIs displayed on mobile devices216, including but not limited to any input/output devices, such as adisplay monitor, touchpad, touchscreen, microphone, camera, keyboard,and/or mouse. In one embodiment, UI module(s) 214 may be configured toimplement any number or type of UIs, whether tailored for desktop PC ormobile device implementation, including but not limited to the userinterfaces described below with respect to FIGS. 5-9B.

In one embodiment, HR server systems 202 may be configured to implementany number or type of systems configured to manage people or employees,such as individual location information, demographic information,individual desk or office information, individual photographs,individual home addresses, individual equipment assignments, etc. ITserver systems 204 may be configured to implement any number or type ofsystems configured to manage and store individual IT assignments, suchas computer, printer, or mobile device assignments, including device IDs(e.g., MAC ID or serial numbers), an IT profile, a search and/orbrowsing history, a clearance/accessibility level, etc. Asset managementserver systems 206 may be configured to implement any number or type ofsystems configured to manage and store information relating to anyasset, equipment, or component of a facility, such as printer, computer,wireless access point, lab equipment, server, display, projector,television, or any other device or system considered to be an asset ofthe facility. Facilities server systems 208 may be configured toimplement any number or type of systems configured to manage and storeinformation relating to a component of a facility, such as a facilityfloor plan, campus map, global map, facility map, equipment map,amenities map, facility amenities map, and so on. Calendar serversystems 222 may be configured to implement any number or type of systemsconfigured to manage and store information relating to a calendar of anindividual, such as events, locations, times, dates, attendees,documents, attachments, event information, etc. Finance server systems224 may be configured to implement any number or type of systemsconfigured to manage and store information relating to finances, such ascosts for assets and resources usage. Any one or more of HR serversystems 202, IT server systems 204, asset management server systems 206,facilities server systems 208, calendar server systems 222, and/orfinance server systems 224 may be configured to store informationrelating to requests, generate presentations of information, generatetickets for initiating the performance of service or maintenance, storedocuments for printing, calendar events, book locations, and so on.

In one embodiment, request server 205 may be configured to communicatewith one or more of HR server systems 202, IT server systems 204, assetmanagement server systems 206, facilities server systems 208, calendarserver systems 222, and/or finance server systems 224 to perform themethods described herein, whether by wired or wireless communications.For example, request server 205 may include one or more translators orapplication programming interfaces (“APIs”) configured to communicatewith various types of known servers systems for managing assets,equipment, people, facilities, calendars, finances and so on. Inaddition, request server 205 may be configured to facilitate interactionbetween mobile devices 216 and those server systems 202-208, whetherdirectly or indirectly, and whether through the Internet or over LAN orWAN.

As described above, in one embodiment, mobile devices 216 may beconfigured to interact with a facility 100 through, among other means,imaging of indicia 116 (FIG. 1). Accordingly, in one embodiment, system200 of FIG. 2 may be configured to operate in conjunction with exemplaryindicia depicted in FIG. 3. FIG. 3 is a schematic diagram of devices andindicia 300 configured to enable users to identify and submitinformation related to a request for information or services relating toa facility, according to an exemplary embodiment of the presentdisclosure.

For example, as shown in FIG. 3, in one embodiment, a two-dimensionalbarcode 302 a may be displayed on an ID badge 302 of a user, such as anemployee of a company, or a student at an educational institution, orany other organization. Also shown in FIG. 3 are other examples ofidentifiers or indicia, such as a one-dimensional bar code 304 adisplayed on a surface of a piece of equipment, such as a printer 304,and a two-dimensional bar code 306 a displayed on a name plate of a room306, such as an office and/or a conference room. As shown in FIG. 3, amobile device 308 containing an optical component, e.g., a camera, maybe used to capture an image of the identifier or indicia 302 a, 304 a,306 a, associated with the respective entity and transmit the image to aserver for processing a request. Alternatively, mobile device 308 mayread and decode any indicia, or otherwise locally obtain one or moredata elements or unique IDs from the indicia. In one embodiment, a usermay scan his or her own badge 302, containing indicia 302 a (e.g., atwo-dimensional barcode or QR code) to log-in to a mobile application ona mobile device, such as electronic device 114, mobile device 216,and/or mobile device 308. For example, the indicia 302 a may contain aunique ID associated with the user's identity, whether in an HR databasesuch as in an HR server systems 202, or otherwise. The user may then,once logged-in, easily interact, directly or indirectly, with assetsand/or components of a facility 100 (e.g., printer 304 and/or room 306of facilities) to make certain requests for information or servicesrelating to those assets or facilities.

FIG. 4 is a flow diagram of an exemplary method for enabling users toidentify and submit information related to a request for information,printing, or services relating to a facility, according to an exemplaryembodiment of the present disclosure. Specifically, FIG. 4 is aflowchart of a method 400 for fulfilling a request, according to anexemplary embodiment consistent with embodiments of the presentdisclosure. At step 402, a server, such as request server 205, mayreceive, from a user via a mobile device, such as mobile device 216, acommunication regarding an entity, the communication may be entityinformation or an image. For example, the communication may be an imageof the user's identification bar code 302 a on the user's identificationbadge 302. In addition, or alternatively, the communication may be aselection of a piece of equipment from a list of equipment and/or animage of an identifier associated with a piece of equipment, other user,or office, for example, an image of the bar code 304 a of a printer 304,or bar code 306 a of a room 306, or any other identifier.

Based on entity information received and/or the image of the identifierreceived from the user's mobile device, the server, such as a requestserver 205, may access a database to retrieve information regarding theentity associated with the identifier (step 404). For example, requestserver 205 may communicate with the HR server systems 202 to accessinformation regarding the user, based on the user's identification barcode 302 a. As another example, request server 205 may communicate withthe asset management server systems 206 to access information regardinga printer, such as printer 304.

At step 406, request server 205 may determine the location of the mobiledevice 216 from which the entity information and/or image was sent. Thislocation determination may be based, in part, on receiving informationregarding the location of the wireless connection point, such as WAP 134(FIG. 1), which the mobile device 216 connected to in order tocommunicate with request server 205. For example, if the user of themobile device 216 accessed the network 218 by connecting to a stationarywireless port, such as a wireless router connected to the network 220,the server may determine that the user is in close proximity to thestationary wireless port. In addition to, or alternatively requestserver 205 may determine the location of the user using globalpositioning (“GPS”) data of the mobile device 216. The location of theuser may be used by request server 205 to better facilitate the user'srequest. Additionally, or alternatively, the location may be determinedby accessing HR server systems 202 for a default location of a user,such as a user's office or desk, determined by accessing assetmanagement server systems 206 for a location of equipment, and/ordetermined by accessing facilities server system 208 for a roomlocation.

At step 408, request server 205 may prompt the user to submit a specificrequest, based on the information retrieved from the other servers. Forexample, in a manner as described above, request server 205 maydetermine that the user is a new employee and has sent an image of anidentifier associated with a printer. Based on this information, requestserver 205 may send a message to the user via the mobile device 216, inthe form of a text, email or other form of communication prompting theuser to submit a request, and may provide a list of options, such as ifthe user would like to connect to the printer, if the user would like toreport a problem with the printer, if the user would like furtherinformation about the printer, etc. As another example, the request maybe a request to access a calendar of the user, a request to create oredit an event for the calendar of the user, and/or a request to share acalendar or an event. The user may then submit a request in response tothe prompt via the mobile device 216.

At step 410, request server 205 may receive the request and process it,such as sending the request to the relevant entity to fulfill therequest and or retrieve any information in the request for the relevantdatabase. Prior to processing the request, request server 205 maydetermine if the user is authorized to make the request. For example,request server 205 may retrieve information about the user from aserver, such as HR server systems 202, based on the user's identifier.HR server systems 202 may include information regarding the type ofrequests that user is authorized to make. For example, HR server systems202 may include various levels of security or permissions associatedwith each user and what type of requests the user may make using thenetwork. Any suitable type or restrictions and categories may beassociated with each user. These restrictions may be set by anadministrator or any other suitable entity. For example, request server205 may retrieve information about the user from HR server systems 202,such as that the user has left the company, and determine, based on thisinformation, that the user is not authorized to make the request. Inthis case, request server 205 may send a communication to the mobiledevice 216 of the user, informing the user that they are not authorizedto make the request. If request server 205 determines, based oninformation retrieved from the database(s), that the user is authorizedto make the request, then the request may proceed to being processed atstep 410.

Step 410 may include steps of sending and receiving communications, suchas messages, documents, print commands, information, instructions, etc.,to servers, printers, peripherals, mobile devices, other users, etc., inorder to fulfill the request. For example, referring to the previousexample, if the user requests, via the mobile device 216, to print to aprinter 304 connected to the network 220, request server 205 maycommunicate with IT server systems 204 and the asset management serversystems 206 to connect the mobile device 216 to the printer 304.

At step 412, depending on the request, request server 205 may check thestatus of the request by communication with the relevant server and thenprovide a status communication to the mobile device 216 regarding therequest. Once the request has been completed, request server 205 maysend a communication to the mobile device 216 at step 414, informing theuser that the request has been completed. At step 416, request server205 may update any databases based on the fulfilled request. Forexample, at step 416, the request server 205 may send finance serversystems 224 information about a print job of a user. The cost of theprint job of the user may then be calculated by finance server systems224. Further, the cost may be associate with the user, a department ofthe user, and/or any other association, as desired.

In an example, in accordance with the present disclosure, the user mayprovide a request prior to sending an image of an identifier; therefore,the step or prompting the user for a request may be skipped. In anotherexample, in accordance with the present disclosure, the user may providea request at the same time as sending an image of the identifier andtherefore the step of prompting the user for a request may be skipped.

FIG. 5 is a screenshot of an exemplary mobile application for enablingusers to identify and submit information related to a request forinformation or services relating to a facility, according to anexemplary embodiment of the present disclosure. Specifically, FIG. 5depicts a mobile application interface 500 by which a user may submitinformation related to a request for information or services relating toa facility. For example, a user may be presented with one or more userelements 502, 504, 506, 508, which may be hyperlinks, buttons, or othermobile application elements that a user can select to initiate making arequest for information or services. For example, as shown in FIG. 5, auser may manipulate user element 502 to issue a request for servicerelating to a “PROBLEM WITH EQUIPMENT.” The user may manipulate userelement 504 to issue a request for information relating to “MYNEIGHBORHOOD.” The user may manipulate user element 506 to issue arequest to “FIND STUFF AROUND ME.” The user may manipulate user element508 to issue a request for a “CONFERENCE ROOM HELPER.” Of course, theindicated user elements are only exemplary of the many types of requestsfor information or services that may be implemented by a mobileapplication of a mobile device 216. When a user selects or otherwisemanipulates one or more of user elements 502-508, the mobile device 216may update its display with another presentation of information, forms,data, request options, etc. to further facilitate the user's request forinformation or services. In one embodiment, a combination of userelements 502-508 available/presented to a user may depend on a user'sidentity. Alternatively, a sub-menu or next screen displayed upon auser's selection of one of user elements 502-508 may depend on a user'sidentity.

Accordingly, FIG. 6 is a schematic diagram of a device and indicia forenabling users to log-in to a mobile application for identifying andsubmitting information related to a request for information or servicesrelating to a facility, according to an exemplary embodiment of thepresent disclosure. Specifically, FIG. 6 depicts an embodiment in whicha user may possess an ID card or badge 602 having, for example, aphotograph, avatar, or other optional image 604, along with amachine-readable identifier or indicia 606. In one embodiment, asdescribed above with respect to FIG. 3 (indicia 302 a of badge 302), theindicia 606 may be a one or two dimensional barcode, such as, forexample, a QR code. Thus, a user may operate his or her mobile device216 (and a mobile application thereon) to capture an image of theindicia 606, or otherwise decode the indicia 606, to obtain at least auser identifier associated with the depicted user 604. Accordingly, amobile application operating on mobile device 216 may identify a user(e.g., through the decoded unique ID), authenticate the user of themobile application as being the owner of the mobile device 216, andtailor one or more presentations of data or generating of tickets basedon the authenticated user identity.

FIGS. 7A-7D are screenshots of an exemplary mobile application forenabling users to identify and submit information related to a requestfor services relating to a facility, according to an exemplaryembodiment of the present disclosure. Specifically, FIG. 7A is ascreenshot of an exemplary mobile application interface 700 by which auser may submit a request for service relating to an asset or componentof a facility. For example, a user may submit a request for servicerelating to a printer, fax machine, telephone, furniture, lab equipment,machine, tool, or any other asset within a facility. As shown in FIG.7A, in one embodiment, a user may manipulate various user interfaceelements of interface 700 to generate and submit a request, fortransmission through the mobile device 216.

For example, in one embodiment, the user may select element 702 to scanor otherwise image or decode machine-readable indicia printed on anasset. For example, the user may scan a barcode or QR code printed on alabel of a piece of equipment, as shown with respect to the printer ofFIG. 3. Alternatively, the user may select user element 704 to manuallyenter an asset tag or unique ID number using an alphanumeric keyboard ofthe user's device. In addition, as shown in FIG. 7A, a user maymanipulate user element 706 to indicate a problem type, such as amalfunction of or damage to the selected equipment or asset. The usermay also or alternatively type in a narrative description of a problemusing user element or form 708.

As shown in FIG. 7B, once a user has either successfully scanned anequipment or asset indicia, or manually entered an equipment or assetunique ID, the interface 700 may display profile information 710associated with the equipment or asset. For example, profile information710 may include a description of the asset or equipment; the name,number, ID, etc. of the individual to whom the asset or equipment isoptionally assigned; a physical location of the asset or equipment(e.g., address, building number, room number, lat/long coordinates,etc.); and/or a phone number associated with a location or owner of theequipment or asset. As shown at ticket creation window 712, a user mayenter a problem type, problem details, etc., and then manipulate userelement 714 to snap a photograph of the equipment or asset to assist inlocating, diagnosing, and/or repairing the subject asset or equipment.For example, as shown in FIG. 7C, the user may have uploaded aphotograph 716 of a particular piece of equipment or asset for which theuser is requesting information or service.

Accordingly, based on a user's interaction with the interfaces and userelements described and depicted with respect to FIGS. 7A-7C, system 200of FIG. 2 may operate programmed instructions to execute a method ofprocessing the user's request for service and/or generating a ticket toperform the user's requested service. For example, request server 205may receive the request from a mobile device 216, store the receivedinformation in database(s) 210, execute processor(s) 212 to interactwith one or more of HR server systems 202, IT server systems 204, assetmanagement server systems 206, and facilities server systems 208 toobtain relevant information from those systems, and generate suitablerequests relating to the equipment. In addition, UI module(s) 214 mayupdate a display of information, repair tickets, etc. on a display of amobile device 216. For example, as shown in FIG. 7D, processor(s) 212may interact with one or more of HR server systems 202, IT serversystems 204, asset management server systems 206, and facilities serversystems 208 to generate a ticket, and interact with UI module(s) 214 topresent a ticket and/or ticket number 718 to a user that requested therelated service.

FIGS. 8A-8E are screenshots of an exemplary mobile application forenabling users to identify and submit information related to a requestfor information relating to a facility, according to an exemplaryembodiment of the present disclosure. Specifically, FIG. 8A depicts anexemplary mobile application interface 800 by which a user may submit arequest for information relating to an asset or component of a facility.

For example, a user may submit a request for information relating toavailable building amenities, equipment, directions, policies, etc. Asshown in FIG. 8A, in one embodiment, a user may manipulate various userinterface elements of interface 800 to generate and submit a request,for transmission through the mobile device 216. For example, a user maybe presented with one or more user elements 804, which may behyperlinks, buttons, or other mobile application elements that a usercan select to initiate making a request for information. For example, asshown in FIG. 8A, a user may manipulate one or more of user elements 804to issue requests for information relating to gyms, help centers,receptionists, game rooms, conference rooms, and so on. In oneembodiment, the building amenities displayed in relation to userelements 804 may be sorted based on their respective location relativeto a detected location of the user (i.e., with the closest buildingamenities listed first).

As shown in FIG. 8B, in one embodiment, the mobile application interface800 may display indicia 806 representing individuals within somepredetermined proximity of a detected location of the user. In oneembodiment, the individuals displayed in relation to user elements 806may be sorted based on their respective location relative to a detectedlocation of the user (i.e., with the closest individuals listed first).In one embodiment, the displayed indicia 806 may include a name, officelocation, building location, phone number, or any other usefulinformation stored in relation to the individual.

As shown in FIG. 8C, in one embodiment, the mobile application interface800 may display indicia 808 representing amenities within somepredetermined proximity of a detected location of the user. For example,the amenities may include break areas, cafeterias, conference rooms,copy rooms, restrooms, vending areas, printers, etc. In one embodiment,the amenities displayed in relation to user elements 808 may be sortedbased on their respective location relative to a detected location ofthe user (i.e., with the closest building amenities listed first). Inone embodiment, the displayed indicia 808 may include a name, officelocation, building location, phone number, or any other usefulinformation stored in relation to the amenity.

As shown in FIG. 8D, in one embodiment, the mobile application interface800 may display indicia 810 representing facilities, rooms, or officeswithin some predetermined proximity of a detected location of the user.For example, the facilities may include any type of office or conferenceroom. In one embodiment, the facilities displayed in relation to userelements 810 may be sorted based on their respective location relativeto a detected location of the user (i.e., with the closest buildingfacilities listed first). In one embodiment, the displayed indicia 810may include a name, office location, building location, phone number, orany other useful information stored in relation to the facilities.

In one embodiment, as shown in FIG. 8E, a user may be able to manipulatethe mobile application operating on the mobile device 216 to “check-in”to any desired location. For example, the user may publically orsemi-publically associate himself or herself with some particularlocation by scanning a barcode (e.g., by manipulating user element 812of interface 800) known to have a particular location. For example, theuser may check-in to a particular office or conference room by scanninga barcode or QR code on the door or wall of that room. Alternatively,the user may check-in to the office or room by scanning a barcode or QRcode on a piece of equipment in that room.

FIGS. 9A-9B are screenshots of an exemplary mobile application forenabling users to view their respective calendars by accessing calendarserver systems 222, and create and/or edit events for a user's calendar,according to an exemplary embodiment of the present disclosure.Specifically, FIG. 9A is a screenshot of an exemplary mobile applicationfor a calendar and enabling users to view and/or schedule events,meetings, and/or reminders, according to an exemplary embodiment of thepresent disclosure. Specifically, FIG. 9A depicts a mobile applicationinterface 900 by which a user may view a calendar and events and createand/or edit events for the calendar. For example, a user may bepresented with one or more user elements 902, 904, 906, which may behyperlinks, buttons, or other mobile application elements that a usercan select to review a calendar and event and/or create events for thecalendar of the user. For example, as shown in FIG. 9A, a user maymanipulate user element 902 to select a day, month, and/or year toreview events for the selected date. The user may manipulate userelement 904 to create or edit events for the selected date. The user maymanipulate user element 906 to review one or more events for a selecteddate and/or one or more events near the selected date. Of course, theindicated user elements are only exemplary of the many types of ways toreview, create, and/or edit events that may be implemented by a mobileapplication of a mobile device 216. When a user selects or otherwisemanipulates one or more of user elements 902-906, the mobile device 216may update its display with another presentation of information, forms,data, request options, etc. to further facilitate the user's request forinformation or services by accessing the calendar server system 222. Inone embodiment, a combination of user elements 902-906available/presented to a user may depend on a user's identity.Alternatively, a sub-menu or next screen displayed upon a user'sselection of one of user elements 902-906 may depend on a user'sidentity.

As shown in FIG. 9B, after selecting to create or edit an event, forexample, by interacting with user element 904, the interface 900 maydisplay event information, as shown by elements 908-922, that areassociated with an event of a calendar of the user. The eventinformation may be pre-populated with event information by accessingcalendar server system 222, when creating a new event and/or editing anexisting event. As shown by user element 908, a subject of the meeting,event, reminder, and/or appointment may be entered manually, if desired.

In one embodiment, the user may select user element 910 to scan orotherwise image or decode machine-readable indicia printed on an asset,such as a conference room and/or office. For example, the user may scana barcode or QR code printed, such as indicia 116 of a room 110, asshown with respect to the printer of FIGS. 1 and 3. Alternatively, theuser may select user element 910 to manually enter or select an assettag or unique ID number using an alphanumeric keyboard of a mobiledevice.

User elements 912 and 914 enable a user to manually enter or select astart time and date for an event and an end time and date for the event.The user may select user element 916 to scan or otherwise image ordecode machine-readable indicia printed on an asset, such as a printer,to use. Further, user element 916 may enable a user to manually enter orselect attachments, such as documents, images, files, etc., associatedwith the meeting. User element 918, when selected, may enable theprinting of the attachments. User element 920, when selected, may enablethe printing of the attachments to be queued in a printing queue forprinting at or near the meeting time and date.

As shown by user element 922, a user may enter a memo and/or notesassociated with the event. User element 924 may enable a user to addattendees for the event. The user may select user element 924 to scan orotherwise image or decode machine-readable indicia printed on an asset,such as an ID badge. For example, the user may scan a barcode or QRcode, such as an ID badge 302 of a user, as shown with respect to the IDbadge of FIG. 3. Alternatively, the user may select user element 924 tomanually enter attendees or select attendees based on their name, uniqueID number, etc., using an alphanumeric keyboard of a mobile device. Userelement 926 may save the event to the calendar of the user, which may bestored in the calendar server system 222.

FIG. 10 is a flow diagram of an exemplary method for enabling printingbased on events scheduled in a calendar of a user, according to anexemplary embodiment of the present disclosure. Specifically, FIG. 10 isa flowchart of a method 1000 for fulfilling a print request, accordingto an exemplary embodiment consistent with embodiments of the presentdisclosure. At step 1002, a server, such as request server 205, mayreceive, from a user via a mobile device, such as mobile device 216, acommunication including an identifier associated with the user and aprint request. The print request may include one or more print items tobe printed, such as the attachments of user element 916, as discussedabove in reference to FIG. 9B. In addition, the print request mayinclude printer information, which may identify a printer and/or aprinter location in which the one or more print items are to be printed.The printer information may be a selection of a printer from a list ofprinters, a selection of a location from a list of locations and/or animage of an identifier associated with a printer and/or an identifierassociated with a location, for example, an image of the bar code 304 aof a printer 304, or bar code 306 a of a room 306, or any otheridentifier. The print request may also include time/date information,which may identify a day and time in which the one or more print itemsare to be printed. The time/date information may be retrieved from userelement 912, as discussed above in reference to FIG. 9B.

Based on the print request, the server may determine whether the printrequest includes printer information and/or time/date information (step1004). If the print request does not include printer information and/ortime/date information, the method 1000 proceeds to step 1006. If theprint request includes at least one of printer information and time/dateinformation, the method 1000 proceeds to step 1030.

At step 1006, the server may access a database to retrieve a calendar ofthe user based on the identifier received with the communication. Forexample, request server 205 may communicate with the calendar serversystems 222 to access a calendar of the user associated with theidentifier. Based on the accessed calendar of the user, the server maydetermine whether an event is scheduled for a time of interest. The timeof interest may be a current time and date, a period before a currenttime and date and including the current time and date, a period before acurrent time and date, a current time and date and a period after, aperiod after a current time and date, a period around a current time anddate, and/or a period around a current time and date and including thecurrent time and date. If there is no scheduled event for time ofinterest, the method 1000 proceeds to step 1010. If there is a scheduledevent for the time of interest, the method 1000 proceeds to step 1022.

At step 1010, the server may determine a location of the user. Theserver may locate a mobile device of the user from which thecommunication including the print request was sent. This locationdetermination may be based, in part, on receiving information regardingthe location of the wireless connection point, such as WAP 134 (FIG. 1),which the mobile device connected to in order to communicate with theserver. For example, if the user of the mobile device accessed thenetwork 218 by connecting to a stationary wireless port, such as awireless router connected to the network 220, the server may determinethat the user is in close proximity to the stationary wireless port. Inaddition, or alternatively, the server may determine the location of theuser using GPS data of the mobile device. Additionally, oralternatively, the location may be determined by accessing HR serversystems 202 for a default location of the user, such as a user's officeor desk, determined by accessing asset management server systems 206 fora location of equipment, and/or determined by accessing facilitiesserver system 208 for a room location.

After the location of the user has been determined, the server maydetermine whether there are any printers near the location of the user(step 1012). For example, with the location information determined atstep 1010, the server may access asset management server systems 206and/or facilities server systems 208 for locations of one or moreprinters near the location of the user. If there are no printers nearthe location of the user or if the location of the user cannot bedetermined, the method 1000 proceeds to step 1014, in which the one ormore print items are printed to a default printer of the user or at adefault location of the user. If there are printers near the location ofthe user, the method 1000 proceeds to step 1016.

At step 1016, the server may select a printer near the location of theuser and may determine whether the printer is busy. If the printer isnot busy, the method 1000 proceeds to step 1018, in which the one ormore print items may be printed on the printer near the location of theuser. If the printer is busy, the method 1000 proceeds to step 1020, inwhich another printer near the location of the user, if any, is selectedand then proceeds to step 1016.

If there is a scheduled event for the time of interest (step 1008), theserver locates one or more printers near the location of the scheduledevent (step 1022). For example, the server may use the locationinformation for the event, such as the location information provided inuser element 910 of FIG. 9B, and asset management server systems 206and/or facilities server systems 208, to locate one or more printersnear the location of the scheduled event. If there are no printers nearthe location of the event and/or if the location of the event cannot bedetermined, the one or more print items may be printed to a defaultprinter of the user or at a default location of the user.

At step 1024, the server may select a printer near the scheduled eventlocation and may determine whether the printer is busy. If the printeris not busy, the method 1000 proceeds to step 1026, in which the one ormore print items are printed on the printer near the scheduled eventlocation. If the printer is busy, the method 1000 proceeds to step 1028,in which another printer near the scheduled event location, if any, isselected and then proceeds to step 1024.

If the print request includes at least one of printer information andtime/date information (step 1004), the server may determine whether aprinter location was provided with the printer information (1030). Forexample, the server may use the location information for the event whenuser element 918 is selected. The location information provided in userelement 910 of FIG. 9B, and asset management server systems 206 and/orfacilities server systems 208, to locate one or more printers. If theprinter location was not provided, the method 1000 may proceed to step1032. If the printer location was provided, the method 1000 may proceedto step 1036.

At step 1032, the server may determine whether time/date information wasprovided. If time/date information was provided, the server may queuethe one or more one or more print items to be printed at the time andthe date of the time/date information to a default printer of a user(step 1034). If time/date information was not provided, the method 1000proceeds to step 1010.

If the printer location was provided (step 1030), the server may locateone or more printers near the printer location provided (step 1036). Forexample, the server may locate or more printers by accessing assetmanagement server systems 206 for a location of equipment, and/oraccessing facilities server system 208 for a room location of one ormore printers.

After one or more printers are located near the printer locationprovided, the server may determine whether time/date information wasprovided (step 1038). If time/date information was provided, the servermay queue the one or more one or more print items to be printed at thetime and the date of the time/date information to the one or moreprinters located near the printer location provided (step 1046). Iftime/date information was not provided, the method 1000 proceeds to step1040.

At step 1040, the server may select a printer near the location providedand may determine whether the printer is busy. If the printer is notbusy, the method 1000 proceeds to step 1042, in which the one or moreprint items are printed on the printer near the printer locationprovided. If the printer is busy, the method 1000 proceeds to step 1044,in which another printer near the printer location provided, if any, isselected and then proceeds to step 1040.

FIG. 11 is a simplified functional block diagram of a computer that maybe configured as a client, agent, or server for executing the methods ofFIGS. 4 and 10, according to exemplary an embodiment of the presentdisclosure. Specifically, in one embodiment, as shown in FIG. 11, any ofHR server systems 202, IT server systems 204, request server 205, assetmanagement server systems 206, facilities server systems 208, mobiledevices 216, calendar server systems 222, and/or finance server systems224 may be an assembly of hardware 1100 including, for example, a datacommunication interface 1160 for packet data communication. The platformmay also include a central processing unit (“CPU”) 1120, in the form ofone or more processors, for executing program instructions. The platformtypically includes an internal communication bus 1110, program storage,and data storage for various data files to be processed and/orcommunicated by the platform such as ROM 1130 and RAM 1140, although thesystem 1100 often receives programming and data via networkcommunications 1170. The system 1100 also may include input and outputports 1150 to connect with input and output devices such as keyboards,mice, touchscreens, monitors, displays, etc. Of course, the variousserver functions may be implemented in a distributed fashion on a numberof similar platforms, to distribute the processing load. Alternatively,the servers may be implemented by appropriate programming of onecomputer hardware platform.

Program aspects of the technology may be thought of as “products” or“articles of manufacture” typically in the form of executable codeand/or associated data that is carried on or embodied in a type ofmachine-readable medium. “Storage” type media include any or all of thetangible memory of the computers, processors or the like, or associatedmodules thereof, such as various semiconductor memories, tape drives,disk drives and the like, which may provide non-transitory storage atany time for the software programming. All or portions of the softwaremay at times be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another, forexample, from a management server or host computer of the mobilecommunication network into the computer platform of a server and/or froma server to the mobile device. Thus, another type of media that may bearthe software elements includes optical, electrical and electromagneticwaves, such as used across physical interfaces between local devices,through wired and optical landline networks and over various air-links.The physical elements that carry such waves, such as wired or wirelesslinks, optical links, or the like, also may be considered as mediabearing the software. As used herein, unless restricted tonon-transitory, tangible “storage” media, terms such as computer ormachine “readable medium” refer to any medium that participates inproviding instructions to a processor for execution.

While the presently disclosed sharing application, methods, devices, andsystems are described with exemplary reference to mobile applicationsand to transmitting HTTP data, it should be appreciated that thepresently disclosed embodiments may be applicable to any environment,such as a desktop or laptop computer, an automobile entertainmentsystem, a home entertainment system, etc. Also, the presently disclosedembodiments may be applicable to any type of Internet protocol that isequivalent or successor to HTTP.

The many features and advantages of the disclosure are apparent from thedetailed specification, and thus, it is intended by the appended claimsto cover all such features and advantages of the disclosure which fallwithin the true spirit and scope of the disclosure. Further, sincenumerous modifications and variations will readily occur to thoseskilled in the art, it is not desired to limit the disclosure to theexact construction and operation illustrated and described, andaccordingly, all suitable modifications and equivalents may be resortedto, falling within the scope of the disclosure.

Other embodiments of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the invention being indicated by the following claims.

1-20. (canceled)
 21. A computer-implemented method for dynamic mobile printing based on scheduled events, the method comprising: receiving, from a device associated with a user, an identifier associated with the user and a print request, the print request including one or more print items to be printed and a time of interest; accessing, by a server, a calendar of the user based on the received identifier associated with the user; determining, by the server, a location of a printer to print the based on the calendar of the user and the time of interest; and transmitting, by the server, the one or more print items to the printer at the determined location.
 22. The method of claim 21, further comprising: determining, by the server, whether the printer at the determined location is busy; locating, by the server, a second printer near the printer at the determined location when the printer at the determined location is busy; and transmitting, by the server, the one or more print items to the second printer.
 23. The method of claim 21, further comprising: determining, by the server, a location of the user when a location of a printer to print the based on the calendar of the user and the time of interest is not determined; locating, by the server, a printer near a location of the user when the location of the user is determined; and transmitting, by the server, the one or more print items to the printer near the location of the user.
 24. The method of claim 21, further comprising: determining, by the server, a location of the user when a location of a printer to print the based on the calendar of the user and the time of interest is not determined; and transmitting, by the server, the one or more print items to a default printer when the location of the user is not determined.
 25. The method of claim 23, further comprising: determining, by the server, whether the printer near the location of the user is busy; locating, by the server, a second printer near the location of the user when the printer near the location of the event is busy; and transmitting, by the server, the one or more print items to the second printer near the location of the user.
 26. The method of claim 21, wherein the print request further includes a print time in which the one or more print items is to be printed, and wherein queuing the one or more print items to print to a default printer at the print time when the print request includes a print time.
 27. The method of claim 21, wherein the identifier associated with the user is captured by the device associated with the user.
 28. The method of claim 21, wherein the time of interest is at least one of a current time and date, a period before a current time and date and including the current time and date, a period before a current time and date, a current time and date and a period after, a period after a current time and date, a period around a current time and date, and/or a period around a current time and date and including the current time and date.
 29. The method of claim 21, wherein a location of an event of the calendar is captured by the device associated with the user.
 30. A system for dynamic mobile printing based on scheduled events, the system comprising: a memory storage device storing instructions for dynamic mobile printing based on scheduled events; and one or more processors configured to execute the instructions to perform a method including: receiving, from a device associated with a user, an identifier associated with the user and a print request, the print request including one or more print items to be printed and a time of interest; accessing a calendar of the user based on the received identifier associated with the user; determining a location of a printer to print the based on the calendar of the user and the time of interest; and transmitting the one or more print items to the printer at the determined location.
 31. The system of claim 30, wherein the processor is further configured for: determining whether the printer at the determined location is busy; locating a second printer near the printer at the determined location when the printer at the determined location is busy; and transmitting the one or more print items to the second printer.
 32. The system of claim 30, wherein the processor is further configured for: determining a location of the user when a location of a printer to print the based on the calendar of the user and the time of interest is not determined; locating a printer near a location of the user when the location of the user is determined; and transmitting the one or more print items to the printer near the location of the user.
 33. The system of claim 30, wherein the processor is further configured for: determining a location of the user when a location of a printer to print the based on the calendar of the user and the time of interest is not determined; and transmitting the one or more print items to a default printer when the location of the user is not determined.
 34. The system of claim 32, wherein the processor is further configured for: determining whether the printer near the location of the user is busy; locating a second printer near the location of the user when the printer near the location of the event is busy; and transmitting the one or more print items to the second printer near the location of the user.
 35. The system of claim 30, wherein the print request further includes a print time in which the one or more print items is to be printed, and wherein queuing the one or more print items to print to a default printer at the print time when the print request includes a print time.
 36. The system of claim 30, wherein the an identifier associated with the user is captured by the device associated with the user.
 37. The system of claim 30, wherein the time of interest is at least one of a current time and date, a period before a current time and date and including the current time and date, a period before a current time and date, a current time and date and a period after, a period after a current time and date, a period around a current time and date, and/or a period around a current time and date and including the current time and date.
 38. The system of claim 30, wherein a location of an event of the calendar is captured by the device associated with the user.
 39. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to execute a method for dynamic mobile printing based on scheduled events, the method comprising: receiving, from a device associated with a user, an identifier associated with the user and a print request, the print request including one or more print items to be printed and a time of interest; accessing, by a server, a calendar of the user based on the received identifier associated with the user; determining, by the server, a location of a printer to print the based on the calendar of the user and the time of interest; and transmitting, by the server, the one or more print items to the printer at the determined location.
 40. The computer-readable medium of claim 39, wherein the further comprises: determining, by the server, whether the printer at the determined location is busy; locating, by the server, a second printer near the printer at the determined location when the printer at the determined location is busy; and transmitting, by the server, the one or more print items to the second printer. 